[FreshEyes] Prune locks#12
[FreshEyes] Prune locks#12adamjonas wants to merge 10 commits intobitcoin-fresheyes-staging-master-19463from
Conversation
Including desc member of PruneLockInfo for a human-readable description
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
This is an OUTDATED review comment as the original pull request may have been rebased or force-pushed
|
|
This is an OUTDATED review comment as the original pull request may have been rebased or force-pushed
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
|
An author commented here with:
|
The author luke-jr wrote the following PR called Prune locks, issue number 19463 in bitcoin/bitcoin cloned by FreshEyes below:
This adds the ability to have any number of internal or external locks to prevent pruning specific block ranges.
Some examples where this would be useful:
By design, users retain complete control over prune locks, and can delete them out from under applications using them. This is to avoid circumstances where a prune lock has been set, by an application that may no longer be used.